-
Notifications
You must be signed in to change notification settings - Fork 16.3k
[v3-1-test] Update refresh token flow #58649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
5d2077f to
1f656d4
Compare
pierrejeambrun
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be backported? Original PR is marked for 3.2
We discussed it in #56614 (comment) and I think the problem is that refreshing keycloak token does not work without it in 3.1.*, so @vincbeck attempted to back-port it. |
|
Successfully it seems |
bugraoz93
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Vincent!
|
It shouldn't impact as long as providers implements refresh logic which wasn't the case for 3.1 |
|
Changed milestone of the original PR to 3.1.4 |
Resolves #56614.
Back-port of #55506.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.